Scheduling Request (SR) Enhancements for 5G Real-Time Extended Reality (XR) Services

ABSTRACT

A user equipment (UE) includes a transceiver and a processor that is configured to identify a plurality of flows corresponding to data to be sent in an uplink (UL) direction. The processor is also configured to map a subset of the plurality of flows to a logical channel (LCH) of a plurality of LCHs. The processor is further configured to multiplex two or more scheduling requests (SRs) into an integrated SR for requesting one or more physical uplink control channel (PUCCH) resources corresponding to each flow of the subset of the plurality of flows of at least one LCH of the plurality of LCHs. Each SR included in the integrated SR corresponds to an SR for the data associated with at least one flow of the subset of the plurality of flows.

TECHNICAL FIELD

This application relates generally to wireless communication systems,including methods and systems for various enhancements for a schedulingrequest (SR) for an extended reality (XR) service, such as a 5Greal-time XR service.

BACKGROUND

Wireless mobile communication technology uses various standards andprotocols to transmit data between a base station and a wirelesscommunication device. Wireless communication system standards andprotocols can include, for example, 3rd Generation Partnership Project(3GPP) long term evolution (LTE) (e.g., 4G), 3GPP new radio (NR) (e.g.,5G), and IEEE 802.11 standard for wireless local area networks (WLAN)(commonly known to industry groups as Wi-Fi©).

As contemplated by the 3GPP, different wireless communication systemsstandards and protocols can use various radio access networks (RANs) forcommunicating between a base station of the RAN (which may alsosometimes be referred to generally as a RAN node, a network node, orsimply a node) and a wireless communication device known as a userequipment (UE). 3GPP RANs can include, for example, global system formobile communications (GSM), enhanced data rates for GSM evolution(EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN),Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and/orNext-Generation Radio Access Network (NG-RAN).

Each RAN may use one or more radio access technologies (RATs) to performcommunication between the base station and the UE. For example, theGERAN implements GSM and/or EDGE RAT, the UTRAN implements universalmobile telecommunication system (UMTS) RAT or other 3GPP RAT, theE-UTRAN implements LTE RAT (sometimes simply referred to as LTE), andNG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NRRAT, or simply NR). In some deployments, the E-UTRAN may also implementNR RAT. In some deployments, NG-RAN may also implement LTE RAT.

A base station used by a RAN may correspond to that RAN. One example ofan E-UTRAN base station is an Evolved Universal Terrestrial Radio AccessNetwork (E-UTRAN) Node B (also commonly denoted as evolved Node B,enhanced Node B, eNodeB, or eNB). One example of an NG-RAN base stationis a next generation Node B (also sometimes referred to as a g Node B orgNB).

A RAN provides its communication services with external entities throughits connection to a core network (CN). For example, E-UTRAN may utilizean Evolved Packet Core (EPC), while NG-RAN may utilize a 5G Core Network(5GC).

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure number in which that element is first introduced.

FIG. 1 shows an example wireless communication system, according toembodiments described herein.

FIG. 2 illustrates an example SR multiplexing, according to embodimentsdescribed herein.

FIG. 3 illustrates a first example mapping of quality of service (QoS)flows to a logical channel (LCH) and a corresponding integrated SR basedon various sub-flows of each individual SR of the integrated SR,according to embodiments described herein.

FIG. 4 illustrates a second example mapping of QoS flows to an LCH and acorresponding integrated SR based on various sub-flows of eachindividual SR of the integrated SR, according to embodiments describedherein.

FIG. 5 illustrates a third example mapping of QoS flows to an LCH and acorresponding integrated SR based on various sub-flows of eachindividual SR of the integrated SR, according to embodiments describedherein.

FIG. 6 illustrates a fourth example mapping of QoS flows to an LCH and acorresponding integrated SR based on various sub-flows of eachindividual SR of the integrated SR, according to embodiments describedherein.

FIG. 7 illustrates a fifth example mapping of QoS flows to an LCH and acorresponding integrated SR based on various sub-flows of eachindividual SR of the integrated SR, according to embodiments describedherein.

FIG. 8 illustrates an example flow-chart of operations that may beperformed by a user equipment, according to embodiments describedherein.

FIG. 9 illustrates an example flow-chart of operations that may beperformed by a base station, according to embodiments described herein.

FIG. 10 illustrates an example architecture of a wireless communicationsystem, according to embodiments described herein.

FIG. 11 illustrates a system for performing signaling between a wirelessdevice and a network device, according to embodiments described herein.

DETAILED DESCRIPTION

In the present disclosure, various embodiments are related to systemsand methods for SR enhancements for an XR service (referred to hereinmore simply as just “XR”) or other special service (e.g., a 5G real-timeXR service). In particular, various embodiments for SR enhancements forXR service, as described herein, may be related to XR-specific capacityimprovements including, but not limited to, providing efficient resourceallocation and scheduling for XR service characteristics. As examples,the XR service characteristics may be related to periodicity, variousflows (e.g., call flows, quality of service (QoS) flows, and so on),jitter, latency, reliability, and so on. The efficient resourceallocation and scheduling may be provided using a mechanism likesemi-persistent scheduling (SPS), configured grants (CGs), dynamicscheduling, dynamic grants, and so on. Various embodiments, as describedherein, may also provide improvements for XR service specific powersaving techniques, to accommodate the XR service characteristics. Insome embodiments, the XR service specific power saving techniques may berelated to physical downlink control channel (PDCCH) monitoringenhancements and/or connected mode discontinuous reception (C-DRX)enhancements.

In recent studies in 3GPP, under objectives of XR-awareness in a radioaccess network (RAN), uplink (UL) and downlink (DL) XR service trafficcharacteristics, QoS metrics, and/or application layer attributes areidentified as beneficial to a base station, which may be used for XRservice specific traffic handling.

In some embodiments, an example of the XR service specific traffichandling may include a buffer status reporting (BSR) procedure that isused by a user equipment (UE) to provide information about an amount ofdata that the UE would like to send to a base station in the ULdirection. Based on the amount of data pending at the UE fortransmission in the UL direction, via a physical uplink shared channel(PUSCH), the base station may allocate a minimum amount of UL grant,based on availability of the PUSCH resource in terms of resource blocks(RBs).

In some embodiments, the BSR procedure may use a 5-bit or 8-bit buffersize field to inform the base station about the amount of data for whichthe UE is requesting an UL grant from the base station. The buffer sizefield of 5-bits may be used as described in Table 6.1.3.1-1 of 3GPPTechnical Specification (TS) 38.321, and the buffer size field of 8-bitsmay be used as described in Table 6.1.3.1-2 of 3GPP TS 38.321. Thebuffer size field may identify a total amount of data for PUSCHtransmission as calculated based on the data volume calculationprocedure described in 3GPP TS 38.322 and 3GPP TS 38.323. The totalamount of data may correspond with data across all logical channels(LCHs) of an LCH group after a media access controller (MAC) protocoldata unit (PDU) is built. By way of a non-limiting example, after an LCHprioritization procedure, a value of the buffer size field may be zero.In some embodiments, the amount of data may be indicated in a number ofbytes. The 5-bits buffer size field may correspond with a short BSRformat or a short truncated BSR format, and the 8-bits buffer size fieldmay correspond with a long BSR format or a long truncated BSR format.

In some embodiments, for the long BSR format and/or the long truncatedBSR format, the buffer size fields may be included in an ascending orderbased on the logical channel group (LCG) index. By way of a non-limitingexample, for the long truncated BSR format, the number of buffer sizefields included in an SR may be maximized without exceeding the numberof padding bits.

In some embodiments, in a pre-emptive BSR procedure, the buffer sizefield may identify a total amount of data expected to arrive at anintegrated access and backhaul mobile termination (IAB-MT) where thepre-emptive BSR procedure is triggered. The total amount of dataexpected to arrive at the IAB-MT may not include a volume of datacurrently available in the IAB-MT. In some embodiments, the pre-emptiveBSR format may be identical to the long BSR format bit that uses 8-bitsof buffer field.

Accordingly, various embodiments described herein may provide solutionsfor SR indication, SR indication optimization using, for example, SRmultiplexing, payload concatenation, and so on. In some embodiments, asingle SR (or an integrated SR) may be generated from a plurality of SRscorresponding to one or more LCHs and/or one or more flows (e.g., callflows, or QoS flows).

Reference will now be made in detail to representativeembodiments/aspects illustrated in the accompanying drawings. Thefollowing description is not intended to limit the embodiments to onepreferred embodiment. On the contrary, it is intended to coveralternatives, combinations, modifications, and equivalents as can beincluded within the spirit and scope of the described embodiments asdefined by the appended claims.

FIG. 1 shows an example wireless communication system, according toembodiments described herein. As shown in FIG. 1 , a wirelesscommunication system 100 may include base stations 102 and 104 and a UE106. In some embodiments, the base stations 102 and/or 104 may be aneNb, an eNodeB, a gNodeB, or an access point (AP) in a RAN and maysupport one or more radio access technologies, such as 4G, 5G, 5G newradio (5G NR), and so on. The UE 106 may be a phone, a smart phone, atablet, a smartwatch, an Internet-of-Things (IoT) device, a vehicle, andso on.

In some embodiments, the UE 106 may have data associated with flowsrelated to XR service to be sent in the UL direction using PUSCH. The UEmay therefore send an SR for allocating one or more RBs corresponding tothe amount of the data associated with the flows related to the XRservice to be sent in the UL direction for an LCH or an LCG. The amountof the data to be sent in the UL direction for which RBs are requestedfrom the base station 102 or 104 may be indicated using one or morebits. By way of a non-limiting example, a 5-bit or 8-bit buffer sizefield, as described herein, may be used for SR indication in some XRservice scenarios.

By way of a non-limiting example, the UE 106 may have data related to XRservice traffic corresponding to an audio stream and/or a data stream ofa constant-bit rate. The UE 106 may, therefore, use a single-bit SRbuffer size field for an SR indication. Similarly, for XR servicetraffic corresponding to a pause/control stream, which may be of aconstant-bit rate, the UE 106 may use a single-bit SR buffer size fieldfor an SR indication. Upon receiving a single-bit SR indication, thebase station may allocate RBs corresponding to a predetermined number ofbytes of data to be sent in the UL direction. The predetermined numberof bytes of data may be determined according to the constant-bit rateconsistent with the type of XR service traffic such as the audio stream,the data stream, the pause/control stream, and/or other constant-bitrate streams or scenarios.

However, XR service traffic related to a video stream may have avariable-bit rate, and the UE 106 may therefore use more than one bit,for example, 5-bits or 8-bits, in an SR indication. Further, the XRservice traffic related to the video stream may follow a distribution ofdata, for example, according to a truncated Gaussian distributionformat, an SR indication may be optimized by indicating the buffer datasize as a quantized buffer data size. The buffer data size may bequantized using a uniform quantizer and/or a non-uniform quantizer.

In some embodiments, the uniform quantizer may be based on a buffer datasize associated with an SR configuration. For example, in an SRindication using 2-bits to communicate buffer data size, a value “00”may be used for a buffer data size between [μ−σ/2, μ+σ/2], a value “01”may be used for a buffer data size between [1, μ−σ/2], a value “10” maybe used for a buffer data size between [μ+σ/2, 1], and so on. Here, μand σ may be configured in an SR configuration.

In some embodiments, the non-uniform quantizer may be based on aquantization step that is specified by the base station 102 or 104 tothe UE 106 in a radio resource control (RRC) signaling and/or mediaaccess controller (MAC) control element (MAC CE). Accordingly, asdescribed herein, in accordance with some embodiments, an SR indicationmay be optimized. Further improvements or enhancements corresponding tothe SR indication with respect to multiple SR indications associatedwith various call flows and/or data associated with different prioritiesare described below in reference to FIG. 2 .

FIG. 2 illustrates an example SR multiplexing, according to embodimentsdescribed herein. In some embodiments, a physical uplink control channel(PUCCH) resource set or a PUCCH resource list may be used for an SR. Asdescribed herein, different flows may be associated with different SRs.Each SR of the different SRs may thus be associated with a differentamount of data or payload size. Further, the UE may have data to be sentin the UL direction associated with one or more different flows, such asdata flows, call flows, and/or QoS flows.

In some embodiments, the UE 106 may send an SR based on an SRconfiguration that is associated with an XR service scenario and/or aflow, such as a data flow, a call flow, and/or a QoS flow. The SRconfiguration may be associated with the PUCCH resource list includingone or more PUCCH resources. A PUCCH resource from the PUCCH resourcelist may be selected based on the payload size. For example, as shown indiagram 200, SR configurations SR Config-1 202 and SR-Config-2 204 maybe configured at the UE 106 by the base station 102 or 104. By way of anon-limiting example, the SR Config-1 202 may include a PUCCH resourcelist including PUCCH resources PUCCH-1 202 a and PUCCH-2 202 b.Similarly, he SR Config-2 may include a PUCCH resource list includingPUCCH resource PUCCH-3 204 a and PUCCH-4 204 b. The UE may select aPUCCH resource according to the payload size from an SR Config thatcorresponds with the flow or the XR service scenario corresponding tothe data to be sent in the UL direction.

As described herein, the data to be sent in the UL direction may beassociated with different XR service scenarios. Accordingly, the data tobe sent in the UL direction may have a different priority; some data mayhave a higher priority in comparison with other data. In someembodiments, the UE may send an SR for only higher priority data, anddrop an SR for lower priority data.

In some embodiments, when the UE 106 has data associated with differentpriorities or flows to be sent in the UL direction or, in other words,where there is a collision between SRs associated with data of differentpriorities or flows to be sent to the base station 102 or 104, an SR maybe selected based on a priority associated with a corresponding SRconfiguration. Additionally, or alternatively, a priority associatedwith a PUCCH resource of a PUCCH resource list of the SR configurationmay be used to select a PUCCH resource for the SR. By way of anon-limiting example, the priority may be determined based on aschedulingRequestID.

In some embodiments, multiple SRs may be multiplexed and an integratedSR (or a single SR) may be generated and transmitted by the UE 106 tothe base station 102 or 104. For example, based on the flow and/or thepayload size, the UE may have two SRs, SR-1 218 and SR-2 220, in whichthe UE may have selected PUCCH resources, the PUCCH-1 202 a and thePUCCH-3 204 a, respectively. The UE may generate the integrated SR 208in which the UE 106 may select a PUCCH resource PUCCH-2 202 b for theintegrated SR 208. Thus, the UE may send the integrated SR 208 insteadof two separate SRs 218 and 220. Even though the present disclosuredescribes multiplexing two SRs into an integrated SR, more than two SRsmay be multiplexed into an integrated SR.

In some embodiments, when multiple SRs are multiplexed into anintegrated SR, payload or data corresponding to each SR of the multipleSRs integrated into the integrated SR may be concatenated according to,for example, an ascending or descending order of a schedulingRequestIdof an SR, or a host SR's schedulingRequestId. As described herein, SRs218 and 220 are integrated into the integrated SR 208, which includes aPUCCH resource PUCCH-2 202 b, and the SR-1 218 is the host SR of theintegrated SR.

In some embodiments, when the payload from multiple SRs are concatenatedas described herein, depending on whether a positive SR-1, a positiveSR-2, and/or a positive integrated SR are generated, for the same PUCCHresource, the payload size may be different. However, to avoid the basestation from having to take extra steps to determine the payload sizefor the same PUCCH resource, a base station blind detection techniquemay be used. In one example, the base station blind detection techniquemay use a base station configuration. Additionally, or alternatively, anSR (for example, the integrated SR) may be split into two parts. By wayof a non-limiting example, splitting of the SR into two parts may beperformed in a similar way that channel state information (CSI) is splitinto two parts.

In some embodiments, a first part of the SR split into two parts mayinclude a bitmap indicating a presence or absence of an SR, and a secondpart of the SR split into two parts may include concatenated payloads ofeach SR associated with the integrated SR. For example, a bitmap value“10” may indicate a presence of SR-1 alone, a bitmap value “11” mayindicate a presence of both SR-1 and SR-2, and so on.

In the diagram 200, an SR Config-3 206 including a PUCCH resource listof PUCCH resources PUCCH-5 206 a, PUCCH-6 206 b, and PUCCH-7 206 c isalso shown. Based on the flow and/or the XR service scenario, and apayload size, the UE 106 may select the PUCCH resource PUCCH-5 206 a foran SR SR-3 210, which has a host-SR of SR-3 as described herein as aPUCCH resource used for this SR belonging to the SR Config-3 206 of SR-3210.

Accordingly, in some embodiments, when the UE 106 multiplexes multipleSRs, the UE may multiplex SRs in multiple stages. For example, in afirst stage the SR-1 218 and the SR-2 220 may be multiplexed into theintegrated SR 208, and then subsequently the SR-3 210 may also bemultiplexed with the SR-1 218 and the SR-2 220 into the integrated SR.Accordingly, an order of multiplexing, e.g., the multiplexing history ofthe SRs, may be presented using a bitmap for the two-part SR. Forexample, the multiplexing history of the SRs may be presented in thebitmap using a priority of the host-SR. For example, a first part of thetwo-part SR 212 may be represented in a bitmap as [11b2] 214 when apriority associated with the SR-3 210 is higher than the priorityassociated with the host SR SR-1 218, or [1b21] 216 when a priorityassociated with a host SR SR-1 218 is higher than the priorityassociated with the host SR SR-3 210.

Accordingly, as described herein in accordance with some embodiments, inaddition to 1-bit SR, an SR may use multiple bits (e.g., 2 or more bits)to report a finer granularity or additional information corresponding toLCHs or an LCG associated with an SR. Using multiple bits for the SR mayrequire additional changes at a physical (PHY) layer.

Additionally, or alternatively, multiple SRs may be mapped as a group toconstruct a composite SR (e.g., a single SR or an integrated SR). EachSR mapped to the integrated SR may be an SR of 1-bit, and the integratedSR may convey more information by extending the number of bits from each1-bit SR.

In some embodiments, and by way of a non-limiting example, a group of1-bit SRs (e.g., an integrated SR) may be associated with the same LCHor LCG, and a different SR of the group of 1-bit SRs may be associatedwith a different priority, a different XR service traffic stream, and/ora different QoS flow, thereby allowing for more fine-granularprioritization and/or identification/association of XR service trafficstreams, and improving resource allocation. For example, a group of SRsmay be linked with an LCH that is associated with multiple QoS flows,and each QoS flow may use its own SR. Further, an SR priority per LCH orLCG may be allocated by a network in such a way that an LCH or LCG withsub-flows that require further prioritization can utilize a separate SRresource per sub-flow. In some embodiments, a table describing mappingof a QoS flow to an SR may be used as configured by a network and/or abase station. FIG. 3 through FIG. 7 describe such mapping of QoS flowsto an LCH and a corresponding integrated SR based on various sub-flowsof each individual SR of the integrated SR.

FIG. 3 illustrates a first example mapping of QoS flows to an LCH and acorresponding integrated SR based on various sub-flows of eachindividual SR of the integrated SR, in accordance with some embodiments.As shown in a diagram 300, various QoS flows, such as a QoS flow 1 302,a QoS flow 2 304, a QoS flow 3 306, a QoS flow 4 308, a QoS flow 5 310,a QoS flow 6 312, a QoS flow 7 314, a QoS flow 8 316, and a QoS flow 9318, may be mapped to different LCHs. For example, the QoS flow 1 302,the QoS flow 2 304, and the QoS flow 3 306 may be mapped to an LCH LCH1320. Similarly, the QoS flow 4 308 and the QoS flow 5 310 may be mappedto an LCH LCH2 322, and the QoS flow 6 312 and the QoS flow 7 314 may bemapped to an LCH LCH3 324. Here, the QoS flows 1-7 are sub-flows fortheir respective LCHs. The QoS flow 8 316 and the QoS flow 9 318 aremapped to a LCH LCH4 326 and LCH LCH5 328, as individual flows, but notas sub-flows in an SR.

As shown in the diagram 300, multiple SRs may be present based on thedata to be sent in the UL direction. Accordingly, an SR schedulingrequest 330 may be generated by the UE that is associated with the LCH1320 and the LCH2 322.

The scheduling request 330 may be based on multiple SRs that correspondto various sub-flows such as the QoS flow 1 302, the QoS flow 2 304, andthe QoS flow 3 306 associated with the LCH LCH1 320, and the QoS flow 4308 and the QoS flow 5 310 associated with the LCH LCH2 322. Thescheduling request 330 may be identified based on an ID of aSchedulingRequestConfig that identifies a scheduling requestconfiguration associated with the one or more LCHs of a plurality ofLCHs. Further, one or more PUCCH resources included in the integrated SR330 as SR Group 1 338 may be identified by an identification of ascheduling resource on a PUCCH configured in a PUCCH-Config, such as aschedulingRequestResourceId 1 338 a, a schedulingRequestResourceId 2 338b, and a schedulingRequestResourceId 3 338 c.

The scheduling request 332 may be based on multiple SRs that correspondto various sub-flows such as the QoS flow 6 312, and the QoS flow 7 314associated with the LCH LCH3 324, and identified based on an ID of aSchedulingRequestConfig that identifies a scheduling requestconfiguration associated with the one or more LCHs of a plurality ofLCHs. Further, one or more PUCCH resources included in the integrated SR332 as SR Group 2 340 may be identified by an identification of ascheduling resource on a PUCCH configured in a PUCCH-Config, such as aschedulingRequestResourceId 4 340 a, and a schedulingRequestResourceId 5340 b.

The SR 334 and the SR 336 each may correspond to an LCH LCH3 326 and328, respectively, but are not integrated with other SRs correspondingto other flows, but rather sent as an individual SR 342 and 344,respectively, including a single PUCCH resource identified as aschedulingRequestResourceId 6 342 a, and a schedulingRequestResourceId 7344 a.

In some embodiments, each QoS flow mapped to an LCH may have the same ordifferent priority, and their corresponding SR in the integrated SR maybe ordered based on the priority associated with QoS flow.

FIG. 4 illustrates a second example mapping of QoS flows to an LCH and acorresponding integrated SR based on various sub-flows of eachindividual SR of the integrated SR, in accordance with some embodiments.As shown in a diagram 400, various QoS flows, such as a QoS flow 1 402,a QoS flow 2 404, a QoS flow 3 406, a QoS flow 4 408, a QoS flow 5 410,a QoS flow 6 412, a QoS flow 7 414, a QoS flow 8 416, and a QoS flow 9418, may be mapped to different LCHs. For example, the QoS flow 1 402,the QoS flow 2 404, and the QoS flow 3 406 may be mapped to an LCH LCH1420. Similarly, the QoS flow 4 408 and the QoS flow 5 410 may be mappedto an LCH LCH2 422, and the QoS flow 6 412 and the QoS flow 7 414 may bemapped to an LCH LCH3 424. Here, the QoS flows 1-7 are sub-flows fortheir respective LCHs. The QoS flow 8 416 and the QoS flow 9 418 aremapped to a LCH LCH4 426 and a LCH LCH5 428, respectively, as individualflows, but not as sub-flows in an SR.

As shown in the diagram 400, multiple SRs may be present based on thedata to be sent in the UL direction. Accordingly, an SR schedulingrequest 430 may be generated by the UE that is associated with the LCH1420 and the LCH2 422.

The scheduling request 430 may be based on multiple SRs that correspondto various sub-flows such as the QoS flow 1 402, the QoS flow 2 404, andthe QoS flow 3 406 associated with the LCH LCH1 420, and the QoS flow 4408 and the QoS flow 5 410 associated with the LCH LCH2 422. Thescheduling request 430 may be identified based on aSchedulingRequestConfig identifying dedicated SR resource configured viaMAC-CellGroupConfig associated with the one or more LCHs of a pluralityof LCHs. Further, one or more PUCCH resources included in the integratedSR 430 as SR Group 1 438 may be identified by an identification of an SRconfiguration to which a logical channel is mapped, such as aschedulingRequestId 1 438 a, a schedulingRequestId 2 438 b, and aschedulingRequestId 3 438 c.

The scheduling request 432 may be based on multiple SRs that correspondto various sub-flows such as the QoS flow 6 412, and the QoS flow 7 414associated with the LCH LCH3 424, and identified based on an ID of aSchedulingRequestConfig identifying a dedicated SR resource configuredvia MAC-CellGroupConfig associated with the one or more LCHs of aplurality of LCHs. Further, one or more PUCCH resources included in theintegrated SR 432 as SR Group 2 440 may be identified by anidentification of an SR configuration to which a logical channel ismapped, such as a schedulingRequestId 4 440 a, and a schedulingRequestId5 440 b.

The SR 434 and the SR 436 each may correspond to an LCH LCH3 426 and428, respectively, but are not integrated with other SRs correspondingto other flows, but rather sent as an individual SR 442 and 444,respectively, including a single PUCCH resource identified as aschedulingRequestId 6 442 a, and a schedulingRequestId 7 444 a.

In some embodiments, each QoS flow mapped to an LCH may have the same ora different priority, and their corresponding SR in the integrated SRmay be ordered based on the priority associated with the QoS flow.

FIG. 5 illustrates a third example mapping of QoS flows to an LCH and acorresponding integrated SR based on various sub-flows of eachindividual SR of the integrated SR, in accordance with some embodiments.As shown in a diagram 500, various QoS flows, such as a QoS flow 1 502,a QoS flow 2 504, a QoS flow 3 506, a QoS flow 4 508, a QoS flow 5 510,a QoS flow 6 512, a QoS flow 7 514, a QoS flow 8 516, and a QoS flow 9518, may be mapped to different LCHs. For example, the QoS flow 1 502,the QoS flow 2 504, and the QoS flow 3 506 may be mapped to an LCH LCH1520. Similarly, the QoS flow 4 508 and the QoS flow 5 510 may be mappedto an LCH LCH2 522, and the QoS flow 6 512 and the QoS flow 7 514 may bemapped to an LCH LCH3 524. Here, the QoS flows 1-7 are sub-flows fortheir respective LCHs. The QoS flow 8 516 and the QoS flow 9 518 aremapped to a LCH LCH4 526 and a LCH LCH5 528, respectively, as individualflows, but not as sub-flows in an SR.

As shown in the diagram 500, multiple SRs may be present based on thedata to be sent in the UL direction. Accordingly, an SR schedulingrequest 530 (or a group of SRs 530) may be generated by the UE that isassociated with the LCH1 520 and the LCH2 522.

The scheduling request 530 may be based on multiple SRs that correspondto various sub-flows such as the QoS flow 1 502, the QoS flow 2 504, andthe QoS flow 3 506 associated with the LCH LCH1 520, and the QoS flow 4508 and the QoS flow 5 510 associated with the LCH LCH2 522. One or morePUCCH resources included in the SR 530 may be identified by a schedulingrequest configuration applicable to a logical channel described inLogicalChannelConfig, such as a SchedulingRequestId 1 530 a, aSchedulingRequestId 2 530 b, and a SchedulingRequestId 3 530 c, having acorresponding mapping (e.g., 1:1 mapping) to an identification of ascheduling resource on a PUCCH configured in a PUCCH-Config, such as aSchedulingRequestResourceId 1 530 d, a SchedulingRequestResourceId 2 530e, and a SchedulingRequestResouceId 3 530 f, respectively.

The scheduling request 532 may be based on multiple SRs that correspondto various sub-flows such as the QoS flow 6 512, and the QoS flow 7 514associated with the LCH LCH3 524. One or more PUCCH resources includedin the SR 532 may be identified by a scheduling request configurationapplicable to a logical channel described in LogicalChannelConfig, suchas a SchedulingRequestId 4 532 a, and a SchedulingRequestId 5 532 b,having a corresponding mapping (e.g., 1:1 mapping) to an identificationof a scheduling resource on a PUCCH configured in a PUCCH-Config, suchas a SchedulingRequestResourceId 4 532 c, and aSchedulingRequestResourceId 5 532 d, respectively.

The SR 534 and the SR 536 each may correspond to an LCH LCH3 526 and528, respectively, but are not integrated with other SRs correspondingto other flows, but rather sent as an individual SR 534 and 536,respectively, including a single PUCCH resource identified by ascheduling request configuration applicable to a logical channeldescribed in a LogicalChannelConfig, such as a SchedulingRequestId 6 534a, and a SchedulingRequestId 7 536 a, respectively, and having acorresponding mapping (e.g., 1:1 mapping) to an identification of ascheduling resource on a PUCCH configured in a PUCCH-Config, such as aSchedulingRequestResourceId 6 534 b and a SchedulingRequestResourceId 7536 b, respectively.

In some embodiments, each QoS flow mapped to an LCH may have the same ora different priority, and their corresponding SR in the integrated SRmay be ordered based on the priority associated with QoS flow. Further,the 1:1 mapping of a PUCCH resource identified by a scheduling requestconfiguration application to a logical channel described in aLogicalChannelConfig and an identification of a scheduling resource on aPUCCH configured in a PUCCH-Config is based on their respective priorityat a PHY level.

FIG. 6 illustrates a fourth example mapping of QoS flows to an LCH and acorresponding integrated SR based on various sub-flows of eachindividual SR of the integrated SR, in accordance with some embodiments.As shown in a diagram 600, various QoS flows, such as a QoS flow 1 602,a QoS flow 2 604, a QoS flow 3 606, a QoS flow 4 608, a QoS flow 5 610,a QoS flow 6 612, a QoS flow 7 614, a QoS flow 8 616, and a QoS flow 9618, may be mapped to different LCHs. For example, the QoS flow 1 602,the QoS flow 2 604, and the QoS flow 3 606 may be mapped to an LCH LCH1620. Similarly, the QoS flow 4 608 and the QoS flow 5 610 may be mappedto an LCH LCH2 622, and the QoS flow 6 612 and the QoS flow 7 614 may bemapped to an LCH LCH3 624. Here, the QoS flows 1-7 are sub-flows fortheir respective LCHs. The QoS flow 8 616 and the QoS flow 9 618 aremapped to a LCH LCH4 626 and a LCH LCH5 628, respectively, as individualflows, but not as sub-flows in an SR.

As shown in the diagram 600, multiple SRs may be present based on thedata to be sent in the UL direction. Accordingly, an SR schedulingrequest 630 (or a group of SRs 630) may be generated by the UE that isassociated with the LCH1 620 and the LCH2 622.

The scheduling request 630 may be based on multiple SRs that correspondto various sub-flows such as the QoS flow 1 602, the QoS flow 2 604, andthe QoS flow 3 606 associated with the LCH LCH1 620, and the QoS flow 4608 and the QoS flow 5 610 associated with the LCH LCH2 622. One or morePUCCH resources included in the SR 630 may be identified by a schedulingrequest configuration applicable to a logical channel described inLogicalChannelConfig, such as a SchedulingRequestId 1 630 a, aSchedulingRequestId 2 630 b, and a SchedulingRequestId 3 630 c, having acorresponding mapping (e.g., M:1 mapping) to an identification of ascheduling resource on a PUCCH configured in a PUCCH-Config, such as aSchedulingRequestResourceId 1 630 d, a SchedulingRequestResourceId 2 630e, and a SchedulingRequestResouceId 3 630 f, respectively.

The scheduling request 632 may be based on multiple SRs that correspondto various sub-flows such as the QoS flow 6 612, and the QoS flow 7 614associated with the LCH LCH3 624. One or more PUCCH resources includedin the SR 632 may be identified by a scheduling request configurationapplicable to a logical channel described in LogicalChannelConfig, suchas a SchedulingRequestId 4 632 a and a SchedulingRequestId 5 632 b,having a corresponding mapping (e.g., M:1 mapping) to an identificationof a scheduling resource on a PUCCH configured in a PUCCH-Config, suchas a SchedulingRequestResourceId 4 632 c and aSchedulingRequestResourceId 5 632 d, respectively.

The SR 634 and the SR 636 each may correspond to an LCH LCH3 626 and628, respectively, but are not integrated with other SRs correspondingto other flows, but rather sent as an individual SR 634 and 636,respectively, including a single PUCCH resource identified by ascheduling request configuration applicable to a logical channeldescribed in a LogicalChannelConfig, such as a SchedulingRequestId 6 634a, and a SchedulingRequestId 7 636 a, respectively, and having acorresponding mapping (e.g., M:1 mapping) to an identification of ascheduling resource on a PUCCH configured in a PUCCH-Config, such as aSchedulingRequestResourceId 6 634 b and a SchedulingRequestResourceId 7636 b, respectively.

In some embodiments, each QoS flow mapped to an LCH may have the same ora different priority, and their corresponding SR in the integrated SRmay be ordered based on the priority associated with QoS flow. Further,the M:1 mapping of a PUCCH resource identified by a scheduling requestconfiguration application to a logical channel described in aLogicalChannelConfig and an identification of a scheduling resource on aPUCCH configured in a PUCCH-Config is based on their respective priorityat a PHY level.

FIG. 7 illustrates a fifth example mapping of QoS flows to an LCH and acorresponding integrated SR based on various sub-flows of eachindividual SR of the integrated SR, in accordance with some embodiments.As shown in a diagram 700, various QoS flows, such as a QoS flow 1 702,a QoS flow 2 704, a QoS flow 3 706, a QoS flow 4 708, a QoS flow 5 710,a QoS flow 6 712, a QoS flow 7 714, a QoS flow 8 716, and a QoS flow 9718, may be mapped to different LCHs. For example, the QoS flow 1 702,the QoS flow 2 704, and the QoS flow 3 706 may be mapped to an LCH LCH1720. Similarly, the QoS flow 4 708 and the QoS flow 5 710 may be mappedto an LCH LCH2 722, and the QoS flow 6 712 and the QoS flow 7 714 may bemapped to an LCH LCH3 724. Here, the QoS flows 1-7 are sub-flows fortheir respective LCHs. The QoS flow 8 716 and the QoS flow 9 718 aremapped to a LCH LCH4 726 and a LCH LCH5 728, respectively, as individualflows, but not as sub-flows in an SR.

As shown in the diagram 700, multiple SRs may be present based on thedata to be sent in the UL direction. Accordingly, an SR schedulingrequest 730 (or a group of SRs 730) may be generated by the UE that isassociated with the LCH1 720 and the LCH2 722.

The scheduling request 730 may be based on multiple SRs that correspondto various sub-flows such as the QoS flow 1 702, the QoS flow 2 704, andthe QoS flow 3 706 associated with the LCH LCH1 720, and the QoS flow 4708 and the QoS flow 5 710 associated with the LCH LCH2 722. One or morePUCCH resources included in the SR 730 may be identified by a schedulingrequest configuration applicable to a logical channel described in aLogicalChannelConfig, such as a SchedulingRequestId 1 730 a, aSchedulingRequestId 2 730 b, and a SchedulingRequestId 3 730 c, having acorresponding mapping (e.g., 1:1 or M:1 mapping) to an identification ofa scheduling resource on a PUCCH configured in a PUCCH-Config, such as aSchedulingRequestResourceId 1 730 d, a SchedulingRequestResourceId 2 730e, and a SchedulingRequestResouceId 3 730 f, respectively.

The scheduling request 732 may be based on multiple SRs that correspondto various sub-flows such as the QoS flow 6 712, and the QoS flow 7 714associated with the LCH LCH3 724. One or more PUCCH resources includedin the SR 732 may be identified by a scheduling request configurationapplicable to a logical channel described in LogicalChannelConfig, suchas a SchedulingRequestId 4 732 a, and a SchedulingRequestId 5 732 b,having a corresponding mapping (e.g., 1:1 or M:1 mapping) to anidentification of a scheduling resource on a PUCCH configured in aPUCCH-Config, such as a SchedulingRequestResourceId 4 732 c, and aSchedulingRequestResourceId 5 732 d, respectively.

The SR 734 and the SR 736 each may correspond to an LCH LCH3 726 and728, respectively, but are not integrated with other SRs correspondingto other flows, but rather sent as an individual SR 734 and 736,respectively, including a single PUCCH resource identified by ascheduling request configuration applicable to a logical channeldescribed in LogicalChannelConfig, such as a SchedulingRequestId 6 734a, and a SchedulingRequestId 7 736 a, respectively, and having acorresponding mapping (e.g., 1:1 or M:1 mapping) to an identification ofa scheduling resource on a PUCCH configured in a PUCCH-Config, such as aSchedulingRequestResourceId 6 734 b and a SchedulingRequestResourceId 7736 b, respectively.

In some embodiments, each QoS flow mapped to an LCH may have the same ora different priority, and their corresponding SR in the integrated SRmay be ordered based on the priority associated with QoS flow. Further,the 1:1 or M:1 mapping of a PUCCH resource identified by a schedulingrequest configuration application to a logical channel describedLogicalChannelConfig and an identification of a scheduling resource on aPUCCH configured in a PUCCH-Config may not be based on priority linkingat a PHY level.

FIG. 8 illustrates an example flow-chart of operations that may beperformed by a user equipment, according to embodiments describedherein. As shown in the flow-chart 800, at 802, a UE may identify aplurality of flows corresponding to data to be sent in an uplink (UL)direction. As described herein, the data to be sent in the UL directionmay be associated with various flows (such as various XR service trafficstreams, and/or QoS flows). Accordingly, the data to be sent in the ULdirection may have different priorities corresponding to theirrespective XR service traffic streams and/or QoS flows. By way of anon-limiting example, the term XR service in the present disclosure maybe related to virtual reality and/or augmented reality, and so on.

At 804, the UE may map a subset of the plurality of flows to a logicalchannel of a plurality of logical channels. For example, as shown inFIG. 3 through FIG. 7 , a subset of flows (e.g., the QoS flow 1, the QoSflow 2, and the QoS flow 3) of a plurality of flows (the QoS flows 1-9)may be mapped to an LCH LCH1.

At 806, the UE may multiplex two or more scheduling requests (SRs) intoan integrated SR (or a composite SR) to form a group of SRs forrequesting one or more physical uplink control channel (PUCCH) resourcescorresponding to each flow of the subset of the plurality of flows of atleast one logical channel of the plurality of logical channels. Each SRincluded in the integrated SR may correspond to a scheduling request forthe data associated with at least one flow of the subset of theplurality of flows. While multiplexing the two or more SRs into theintegrated SR is described in detail with reference to variousembodiments described using FIG. 3 through FIG. 7 , multiplexing of theSRs is not described again for brevity.

FIG. 9 illustrates an example flow-chart of operations that may beperformed by a base station, according to embodiments described herein.As shown in the flow-chart 900, at 902, a base station may transmit, toa user equipment (UE), a configuration describing a scheduling request(SR) priority associated with at least one logical channel of aplurality of logical channels. The at least one logical channel may beassociated with a plurality of flows, or one or more flows, mapped toit.

At 904, the base station may receive, from the UE, a single schedulingrequest (SR) (or a composite SR or an integrated SR) for requesting oneor more physical uplink control channel (PUCCH) resources correspondingto the plurality of flows, or one or more flows, of the at least onelogical channel. As described herein, in accordance with someembodiments, the integrated SR may include a plurality of SRs, and eachSR included in the integrated SR may correspond to an SR for ULtransmission of data associated with each flow of the plurality offlows. Accordingly, a first SR and a second SR included in theintegrated SR may have a different priority based on their respectiveflow.

Thus, various embodiments described herein may provide improvement orenhancement to SR in various XR service scenarios.

Embodiments contemplated herein include one or more non-transitorycomputer-readable media storing instructions to cause an electronicdevice, upon execution of the instructions by one or more processors ofthe electronic device, to perform one or more elements of the method800, or 900. In the context of method 800, this non-transitorycomputer-readable media may be, for example, a memory of a UE (such as amemory 1106 of a wireless device 1102 that is a UE, as describedherein). In the context of method 900, this non-transitorycomputer-readable media may be, for example, a memory of a base station(such as a memory 1124 of a network device 1120 that is a base station,as described herein).

Embodiments contemplated herein include an apparatus having logic,modules, or circuitry to perform one or more elements of the method 800,or 900. In the context of method 800, this apparatus may be, forexample, an apparatus of a UE (such as a wireless device 1102 that is aUE, as described herein). In the context of method 900, this apparatusmay be, for example, an apparatus of a base station (such as a networkdevice 1120 that is a base station, as described herein).

Embodiments contemplated herein include an apparatus having one or moreprocessors and one or more computer-readable media, using or storinginstructions that, when executed by the one or more processors, causethe one or more processors to perform one or more elements of the method800, or 900. In the context of method 800, this apparatus may be, forexample, an apparatus of a UE (such as a wireless device 1102 that is aUE, as described herein). In the context of the method 900, thisapparatus may be, for example, an apparatus of a base station (such as anetwork device 1120 that is a base station, as described herein).

Embodiments contemplated herein include a signal as described in orrelated to one or more elements of the method 800, or 900.

Embodiments contemplated herein include a computer program or computerprogram product having instructions, wherein execution of the program bya processor causes the processor to carry out one or more elements ofthe method 800, or 900. In the context of method 800, the processor maybe a processor of a UE (such as a processor(s) 1104 of a wireless device1102 that is a UE, as described herein), and the instructions may be,for example, located in the processor and/or on a memory of the UE (suchas a memory 1106 of a wireless device 1102 that is a UE, as describedherein). In the context of method 900, the processor may be a processorof a base station (such as a processor(s) 1122 of a network device 1120that is a base station, as described herein), and the instructions maybe, for example, located in the processor and/or on a memory of the basestation (such as a memory 1124 of a network device 1120 that is a basestation, as described herein).

FIG. 10 illustrates an example architecture of a wireless communicationsystem, according to embodiments described herein. The followingdescription is provided for an example wireless communication system1000 that operates in conjunction with the LTE system standards and/or5G or NR system standards as provided by 3GPP technical specifications.

As shown by FIG. 10 , the wireless communication system 1000 includes UE1002 and UE 1004 (although any number of UEs may be used). In thisexample, the UE 1002 and the UE 1004 are illustrated as smartphones(e.g., handheld touchscreen mobile computing devices connectable to oneor more cellular networks), but may also comprise any mobile ornon-mobile computing device configured for wireless communication.

The UE 1002 and UE 1004 may be configured to communicatively couple witha RAN 1006. In embodiments, the RAN 1006 may be NG-RAN, E-UTRAN, etc.The UE 1002 and UE 1004 utilize connections (or channels) (shown asconnection 1008 and connection 1010, respectively) with the RAN 1006,each of which comprises a physical communications interface. The RAN1006 can include one or more base stations, such as base station 1012and base station 1014, that enable the connection 1008 and connection1010.

In this example, the connection 1008 and connection 1010 are airinterfaces to enable such communicative coupling, and may be consistentwith RAT(s) used by the RAN 1006, such as, for example, an LTE and/orNR.

In some embodiments, the UE 1002 and UE 1004 may also directly exchangecommunication data via a sidelink interface 1016. The UE 1004 is shownto be configured to access an access point (shown as AP 1018) viaconnection 1020. By way of example, the connection 1020 can comprise alocal wireless connection, such as a connection consistent with any IEEE802.11 protocol, wherein the AP 1018 may comprise a Wi-Fi® router. Inthis example, the AP 1018 may be connected to another network (forexample, the Internet) without going through a CN 1024.

In embodiments, the UE 1002 and UE 1004 can be configured to communicateusing orthogonal frequency division multiplexing (OFDM) communicationsignals with each other or with the base station 1012 and/or the basestation 1014 over a multicarrier communication channel in accordancewith various communication techniques, such as, but not limited to, anorthogonal frequency division multiple access (OFDMA) communicationtechnique (e.g., for downlink communications) or a single carrierfrequency division multiple access (SC-FDMA) communication technique(e.g., for uplink and ProSe or sidelink communications), although thescope of the embodiments is not limited in this respect. The OFDMsignals can comprise a plurality of orthogonal subcarriers.

In some embodiments, all or parts of the base station 1012 or basestation 1014 may be implemented as one or more software entities runningon server computers as part of a virtual network. In addition, or inother embodiments, the base station 1012 or base station 1014 may beconfigured to communicate with one another via interface 1022. Inembodiments where the wireless communication system 1000 is an LTEsystem (e.g., when the CN 1024 is an EPC), the interface 1022 may be anX2 interface. The X2 interface may be defined between two or more basestations (e.g., two or more eNBs and the like) that connect to an EPC,and/or between two eNBs connecting to the EPC. In embodiments where thewireless communication system 1000 is an NR system (e.g., when CN 1024is a 5GC), the interface 1022 may be an Xn interface. The Xn interfaceis defined between two or more base stations (e.g., two or more gNBs andthe like) that connect to the 5GC, between a base station 1012 (e.g., agNB) connecting to the 5GC and an eNB, and/or between two eNBsconnecting to the 5GC (e.g., CN 1024).

The RAN 1006 is shown to be communicatively coupled to the CN 1024. TheCN 1024 may comprise one or more network elements 1026, which areconfigured to offer various data and telecommunications services tocustomers/subscribers (e.g., users of UE 1002 and UE 1004) who areconnected to the CN 1024 via the RAN 1006. The components of the CN 1024may be implemented in one physical device or separate physical devicesincluding components to read and execute instructions from amachine-readable or computer-readable medium (e.g., a non-transitorymachine-readable storage medium).

In embodiments, the CN 1024 may be an EPC, and the RAN 1006 may beconnected with the CN 1024 via an S1 interface 1028. In embodiments, theS1 interface 1028 may be split into two parts, an S1 user plane (S1-U)interface, which carries traffic data between the base station 1012 orbase station 1014 and a serving gateway (S-GW), and the S1-MMEinterface, which is a signaling interface between the base station 1012or base station 1014 and mobility management entities (MMEs).

In embodiments, the CN 1024 may be a 5GC, and the RAN 1006 may beconnected with the CN 1024 via an NG interface 1028. In embodiments, theNG interface 1028 may be split into two parts, an NG user plane (NG-U)interface, which carries traffic data between the base station 1012 orbase station 1014 and a user plane function (UPF), and the S1 controlplane (NG-C) interface, which is a signaling interface between the basestation 1012 or base station 1014 and access and mobility managementfunctions (AMFs).

Generally, an application server 1030 may be an element offeringapplications that use internet protocol (IP) bearer resources with theCN 1024 (e.g., packet switched data services). The application server1030 can also be configured to support one or more communicationservices (e.g., VoIP sessions, group communication sessions, etc.) forthe UE 1002 and UE 1004 via the CN 1024. The application server 1030 maycommunicate with the CN 1024 through an IP communications interface1032.

FIG. 11 illustrates a system 1100 for performing signaling 1138 betweena wireless device 1102 and a network device 1120, according toembodiments described herein. The system 1100 may be a portion of awireless communication system as herein described. The wireless device1102 may be, for example, a UE of a wireless communication system. Thenetwork device 1120 may be, for example, a base station (e.g., an eNB ora gNB) of a wireless communication system.

The wireless device 1102 may include one or more processor(s) 1104. Theprocessor(s) 1104 may execute instructions such that various operationsof the wireless device 1102 are performed, as described herein. Theprocessor(s) 1104 may include one or more baseband processorsimplemented using, for example, a central processing unit (CPU), adigital signal processor (DSP), an application specific integratedcircuit (ASIC), a controller, a field programmable gate array (FPGA)device, another hardware device, a firmware device, or any combinationthereof configured to perform the operations described herein.

The wireless device 1102 may include a memory 1106. The memory 1106 maybe a non-transitory computer-readable storage medium that storesinstructions 1108 (which may include, for example, the instructionsbeing executed by the processor(s) 1104). The instructions 1108 may alsobe referred to as program code or a computer program. The memory 1106may also store data used by, and results computed by, the processor(s)1104.

The wireless device 1102 may include one or more transceiver(s) 1110that may include radio frequency (RF) transmitter and/or receivercircuitry that use the antenna(s) 1112 of the wireless device 1102 tofacilitate signaling (e.g., the signaling 1138) to and/or from thewireless device 1102 with other devices (e.g., the network device 1120)according to corresponding RATs.

The wireless device 1102 may include one or more antenna(s) 1112 (e.g.,one, two, four, or more). For embodiments with multiple antenna(s) 1112,the wireless device 1102 may leverage the spatial diversity of suchmultiple antenna(s) 1112 to send and/or receive multiple different datastreams on the same time and frequency resources. This behavior may bereferred to as, for example, multiple input multiple output (MIMO)behavior (referring to the multiple antennas used at each of atransmitting device and a receiving device that enable this aspect).MIMO transmissions by the wireless device 1102 may be accomplishedaccording to precoding (or digital beamforming) that is applied at thewireless device 1102 that multiplexes the data streams across theantenna(s) 1112 according to known or assumed channel characteristicssuch that each data stream is received with an appropriate signalstrength relative to other streams and at a desired location in thespatial domain (e.g., the location of a receiver associated with thatdata stream). Some embodiments may use single user MIMO (SU-MIMO)methods (where the data streams are all directed to a single receiver)and/or multi user MIMO (MU-MIMO) methods (where individual data streamsmay be directed to individual (different) receivers in differentlocations in the spatial domain).

In some embodiments having multiple antennas, the wireless device 1102may implement analog beamforming techniques, whereby phases of thesignals sent by the antenna(s) 1112 are relatively adjusted such thatthe (joint) transmission of the antenna(s) 1112 can be directed (this issometimes referred to as beam steering).

The wireless device 1102 may include one or more interface(s) 1114. Theinterface(s) 1114 may be used to provide input to or output from thewireless device 1102. For example, a wireless device 1102 that is a UEmay include interface(s) 1114 such as microphones, speakers, atouchscreen, buttons, and the like in order to allow for input and/oroutput to the UE by a user of the UE. Other interfaces of such a UE maybe made up of transmitters, receivers, and other circuitry (e.g., otherthan the transceiver(s) 1110/antenna(s) 1112 already described) thatallow for communication between the UE and other devices and may operateaccording to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

The wireless device 1102 may include an SR module 1116. The SR module1116 may be implemented via hardware, software, or combinations thereof.For example, the SR module 1116 may be implemented as a processor,circuit, and/or instructions 1108 stored in the memory 1106 and executedby the processor(s) 1104. In some examples, the SR module 1116 may beintegrated within the processor(s) 1104 and/or the transceiver(s) 1110.For example, the SR module 1116 may be implemented by a combination ofsoftware components (e.g., executed by a DSP or a general processor) andhardware components (e.g., logic gates and circuitry) within theprocessor(s) 1104 or the transceiver(s) 1110.

The SR module 1116 may be used for various aspects of the presentdisclosure, for example, aspects of FIGS. 1-9 , from the UE perspective.

The network device 1120 may include one or more processor(s) 1122. Theprocessor(s) 1122 may execute instructions such that various operationsof the network device 1120 are performed, as described herein. Theprocessor(s) 1122 may include one or more baseband processorsimplemented using, for example, a CPU, a DSP, an ASIC, a controller, anFPGA device, another hardware device, a firmware device, or anycombination thereof configured to perform the operations describedherein.

The network device 1120 may include a memory 1124. The memory 1124 maybe a non-transitory computer-readable storage medium that storesinstructions 1126 (which may include, for example, the instructionsbeing executed by the processor(s) 1122). The instructions 1126 may alsobe referred to as program code or a computer program. The memory 1124may also store data used by, and results computed by, the processor(s)1122.

The network device 1120 may include one or more transceiver(s) 1128 thatmay include RF transmitter and/or receiver circuitry that use theantenna(s) 1130 of the network device 1120 to facilitate signaling(e.g., the signaling 1138) to and/or from the network device 1120 withother devices (e.g., the wireless device 1102) according tocorresponding RATs.

The network device 1120 may include one or more antenna(s) 1130 (e.g.,one, two, four, or more). In embodiments having multiple antenna(s)1130, the network device 1120 may perform MIMO, digital beamforming,analog beamforming, beam steering, etc., as has been described.

The network device 1120 may include one or more interface(s) 1132. Theinterface(s) 1132 may be used to provide input to or output from thenetwork device 1120. For example, a network device 1120 that is a basestation may include interface(s) 1132 made up of transmitters,receivers, and other circuitry (e.g., other than the transceiver(s)1128/antenna(s) 1130 already described) that enables the base station tocommunicate with other equipment in a network, and/or that enables thebase station to communicate with external networks, computers,databases, and the like for purposes of operations, administration, andmaintenance of the base station or other equipment operably connectedthereto.

The network device 1120 may include an SR module 1134. The SR module1134 may be implemented via hardware, software, or combinations thereof.For example, the SR module 1134 may be implemented as a processor,circuit, and/or instructions 1126 stored in the memory 1124 and executedby the processor(s) 1122. In some examples, the SR module 1134 may beintegrated within the processor(s) 1122 and/or the transceiver(s) 1128.For example, the SR module 1134 may be implemented by a combination ofsoftware components (e.g., executed by a DSP or a general processor) andhardware components (e.g., logic gates and circuitry) within theprocessor(s) 1122 or the transceiver(s) 1128.

The SR module 1134 may be used for various aspects of the presentdisclosure, for example, aspects of FIGS. 1-9 , from a base stationperspective.

For one or more embodiments, at least one of the components set forth inone or more of the preceding figures may be configured to perform one ormore operations, techniques, processes, and/or methods as set forthherein. For example, a baseband processor as described herein inconnection with one or more of the preceding figures may be configuredto operate in accordance with one or more of the examples set forthherein. For another example, circuitry associated with a UE, basestation, network element, etc. as described above in connection with oneor more of the preceding figures may be configured to operate inaccordance with one or more of the examples set forth herein.

Any of the above described embodiments may be combined with any otherembodiment (or combination of embodiments), unless explicitly statedotherwise. The foregoing description of one or more implementationsprovides illustration and description, but is not intended to beexhaustive or to limit the scope of embodiments to the precise formdescribed. Modifications and variations are possible in light of theabove teachings or may be acquired from practice of various embodiments.

Embodiments and implementations of the systems and methods describedherein may include various operations, which may be embodied inmachine-executable instructions to be executed by a computer system. Acomputer system may include one or more general-purpose orspecial-purpose computers (or other electronic devices). The computersystem may include hardware components that include specific logic forperforming the operations or may include a combination of hardware,software, and/or firmware.

The systems described herein pertain to specific embodiments but areprovided as examples. These embodiments can be combined into singlesystems, partially combined into other systems, split into multiplesystems or divided or combined in other ways. In addition, it iscontemplated that parameters, attributes, aspects, etc. of oneembodiment can be used in another embodiment. The parameters,attributes, aspects, etc. are merely described in one or moreembodiments for clarity, and it is recognized that the parameters,attributes, aspects, etc. can be combined with or substituted forparameters, attributes, aspects, etc. of another embodiment unlessspecifically disclaimed herein.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

Although the foregoing has been described in some detail for purposes ofclarity, it will be apparent that changes and modifications may be madewithout departing from the principles thereof. It should be noted thatthere are many alternative ways of implementing both the processes andapparatuses described herein. Accordingly, the present embodiments areto be considered illustrative and not restrictive, and the descriptionis not to be limited to the details given herein, but may be modifiedwithin the scope and equivalents of the appended claims.

1. A user equipment (UE), comprising: a transceiver; and a processorconfigured to: identify a plurality of flows corresponding to data to besent in an uplink (UL) direction; map a subset of the plurality of flowsto a logical channel of a plurality of logical channels; and multiplextwo or more scheduling requests (SRs) into an integrated SR forrequesting one or more physical uplink control channel (PUCCH) resourcescorresponding to each flow of the subset of the plurality of flows of atleast one logical channel of the plurality of logical channels, each SRincluded in the integrated SR corresponding to a scheduling request forthe data associated with at least one flow of the subset of theplurality of flows.
 2. The UE of claim 1, wherein an SR included in theintegrated SR carries information of 1-bit, the informationcorresponding to a payload size of the data associated with a flow ofthe subset of the plurality of flows, the flow of the subset of theplurality flows corresponding to a stream of a constant-bit rate.
 3. TheUE of claim 1, wherein a first SR included in the integrated SR has adifferent priority from a second SR included in the integrated SR. 4.The UE of claim 1, wherein the processor is configured to select the oneor more PUCCH resources for an SR included in the integrated SR inaccord with each flow of the subset of the plurality of flows based on apayload size of the data associated with each flow of the subset of theplurality of flows.
 5. The UE of claim 4, wherein the processor isconfigured to concatenate the data associated with more than one flow ofthe subset of the plurality of flows according to a particularcriterion.
 6. The UE of claim 5, wherein the particular criterion is anascending order of an SR identification (SR ID) of each SR configurationassociated with each of the subset of the plurality of flows.
 7. The UEof claim 1, wherein an SR included in the integrated SR carriesinformation of more than one bit, the information corresponding to apayload size of the data associated with a flow of the subset of theplurality of flows, the flow of the subset of the plurality of flowscorresponding to a stream of a variable-bit rate.
 8. The UE of claim 1,wherein an SR included in the integrated SR is related to a flow of thesubset of the plurality of flows, and the flow of the subset of theplurality flows is related to virtual reality or augmented reality. 9.The UE of claim 1, wherein: the one or more PUCCH resources included inthe integrated SR is identified by an identification of a schedulingresource on a PUCCH configured in a PUCCH-Config; and the integrated SRcorresponds with one or more logical channels of the plurality oflogical channels mapped and identified based on an ID of aSchedulingRequestConfig that identifies a scheduling requestconfiguration associated with the one or more logical channels of theplurality of logical channels.
 10. The UE of claim 1, wherein: the oneor more PUCCH resources included in the integrated SR is identified byan identification of an SR configuration to which the logical channel ismapped as described in a SchedulingRequestConfig configured in aMAC-CellGroupConfig; and the integrated SR corresponds with one or morelogical channels of the plurality of logical channels mapped andidentified based on the SchedulingRequestConfig identifying a dedicatedSR resource configured via the MAC-CellGroupConfig.
 11. The UE of claim1, wherein: the one or more PUCCH resources included in the integratedSR are identified by a scheduling request configuration applicable to alogical channel described in a LogicalChannelConfig having acorresponding mapping to an identification of a scheduling resource on aPUCCH configured in a PUCCH-Config.
 12. The UE of claim 11, wherein: theidentification of the scheduling resource on the PUCCH configured in thePUCCH-Config is mapped to one or more identifications of the schedulingrequest configuration applicable to the logical channel described in theLogicalChannelConfig.
 13. The UE of claim 12, wherein the identificationof the scheduling resource on the PUCCH configured in the PUCCH-Configand the one or more identifications of the scheduling requestconfiguration applicable to the logical channel described in theLogicalChannelConfig are mapped based on a priority at a physical (PHY)layer corresponding to the identification of the scheduling resource onthe PUCCH configured in the PUCCH-Config and the one or moreidentifications of the scheduling request configuration applicable tothe logical channel described in the LogicalChannelConfig.
 14. The UE ofclaim 12, wherein the identification of the scheduling resource on thePUCCH configured in the PUCCH-Config and the one or more identificationsof the scheduling request configuration applicable to the logicalchannel described in the LogicalChannelConfig are mapped irrespective ofa priority at a physical (PHY) layer corresponding to the identificationof the scheduling resource on the PUCCH configured in the PUCCH-Configand the one or more identifications of the scheduling requestconfiguration applicable to the logical channel described in theLogicalChannelConfig.
 15. A method, comprising: identifying a pluralityof flows corresponding to data to be sent in an uplink (UL) direction;mapping a subset of the plurality of flows to a logical channel of aplurality of logical channels; and multiplexing two or more schedulingrequests (SRs) into an integrated SR for requesting one or more physicaluplink control channel (PUCCH) resources corresponding to each flow ofthe subset of the plurality of flows of at least one logical channel ofthe plurality of logical channels into a group of SRs, each SR of thegroup of SRs corresponding to a scheduling request for the dataassociated with each flow of the subset of the plurality of flows. 16.The method of claim 15, wherein the multiplexing the two or more SRsinto the integrated SR comprises multiplexing the two or more SRs intothe integrated SR based on a respective priority corresponding to eachflow of the subset of the plurality of flows.
 17. The method of claim15, wherein the one or more PUCCH resources requested using theintegrated SR are selected based on a payload size of the dataassociated with each flow of the subset of the plurality of flows.
 18. Abase station, comprising: a transceiver; and a processor configured to:transmit, to a user equipment (UE) and via the transceiver, aconfiguration describing a scheduling request (SR) priority associatedwith at least one logical channel of a plurality of logical channels,the at least one logical channel having a plurality of flows mapped tothe at least one logical channel; and receive, from the UE and via thetransceiver, an integrated scheduling request (SR) for requesting one ormore physical uplink control channel (PUCCH) resources corresponding tothe plurality of flows of the at least one logical channel, theintegrated SR including a plurality of SRs, each SR included in theintegrated SR corresponding to an SR for uplink transmission of dataassociated with each flow of the plurality of flows.
 19. The basestation of claim 18, wherein a first SR included in the integrated SRhas a different priority from a second SR included in the integrated SR.20. The base station of claim 18, wherein an SR included in theintegrated SR carries information of 1-bit, the informationcorresponding to a payload size of the data associated with a flow ofthe subset of the plurality of flows, the flow of the subset of theplurality of flows corresponding to a stream of a constant-bit rate.